Techniques for controlling spectrum usage of a hierarchical communication system

ABSTRACT

An access point (AP) device for controlling spectrum usage of a hierarchical communication system, in which a spectrum reserved for an Incumbent is usable by at least one user equipment (UE) for transmission when the spectrum is not required by the Incumbent, is disclosed. The AP device includes a processor configured to receive a message from the Incumbent requesting vacating of a spectrum; generate a group of users affected by the message from the Incumbent requesting vacating of the spectrum; and perform a spectrum management operation on the group of users.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.16/957,735, filed on Jun. 25, 2020, which is a national phaseapplication of PCT Application No. PCT/US2019/015372 filed on Jan. 28,2019, which claims priority to European Application No. 18 156 300.8filed on Feb. 12, 2018, each of which are herein incorporated byreference in their entirety.

FIELD

The disclosure relates to an access point (AP) device and techniques forcontrolling spectrum usage of a hierarchical communication system, inwhich a spectrum reserved for an Incumbent is usable by at least oneuser equipment (UE) for transmission when the spectrum is not requiredby the Incumbent. The disclosure further relates to integration of adecentralized network such as WiFi into a centralized network such asSpectrum Access System (SAS) or Licensed Shared Access (LSA) systemthrough application layer communication using standardized ApplicationProgramming Interfaces (APIs).

BACKGROUND

Spectrum Access System (SAS) based spectrum sharing will be applied inthe US in the 3.5 GHz band (and possibly in further bands in thefuture). In Europe, the so-called Licensed Shared Access (LSA) systemwill be implemented in the 2.3-2.4 GHz band. In SAS three types of usersare defined: i) Incumbent (highest priority), ii) Priority AccessLicense (PAL) User (2^(nd) level of priority) and iii) GeneralAuthorized Access (GAA) Users such as MuLTEfire, etc. with specificchanges to address SAS requirements (such as Incumbent protection,etc.). Currently there is no mechanism defined for an interaction of adecentralized network such as WiFi with a centralized system such as SASin such a manner that the WiFi access is suppressed when an Incumbent isactive and reactivated when the Incumbent is silent.

In the following a technique for controlling spectrum usage in ahierarchical communication system is presented.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings are included to provide a furtherunderstanding of aspects and are incorporated in and constitute a partof this specification. The drawings illustrate aspects and together withthe description serve to explain principles of aspects. Other aspectsand many of the intended advantages of aspects will be readilyappreciated as they become better understood by reference to thefollowing detailed description. Like reference numerals designatecorresponding similar parts.

FIG. 1 is a block diagram of a Spectrum Access System (SAS) 100 forspectrum management according to the FCC regulation.

FIG. 2 is a block diagram of a Licensed Shared Access (LSA) system 200as currently defined in Europe.

FIG. 3 is a schematic diagram illustrating an exemplary WiFi stack 300.

FIG. 4 is a schematic diagram illustrating an exemplary SAS compliantWiFi equipment 400 according to the disclosure.

FIG. 5 is an exemplary message sequence chart illustrating an exemplarymessaging 500 between SAS entities according to the disclosure when anIncumbent arrives.

FIG. 6 is an exemplary message sequence chart illustrating an exemplarymessaging 600 between SAS entities according to the disclosure when theIncumbent does not require the spectrum resource any more.

FIG. 7 is schematic diagram illustrating an exemplary workflow 700 forthe operation of Citizen Broadband Radio System (CBRS) tier-3 usersaccording to the disclosure.

FIG. 8 is an exemplary access point (AP) device 800 according to thedisclosure.

FIG. 9 is an exemplary central controller 900, e.g. an SAS controlleraccording to the disclosure.

FIG. 10 is schematic diagram illustrating a method 1000 for controllingspectrum usage of a hierarchical communication system according to thedisclosure.

FIG. 11 is an exemplary message sequence chart illustrating an exemplarymessaging 1100 between SAS entities according to the disclosure when anIncumbent arrives.

DETAILED DESCRIPTION

In the context of this disclosure, spectrum access systems and spectrumaccess networks are described for sharing spectrum resources betweendifferent radio networks according to a spectrum sharing scheme. Any ofthe radio links described herein may operate according to any one ormore of the following radio communication technologies and/or standardsincluding but not limited to: a Global System for Mobile Communications(GSM) radio communication technology, a General Packet Radio Service(GPRS) radio communication technology, an Enhanced Data Rates for GSMEvolution (EDGE) radio communication technology, and/or a ThirdGeneration Partnership Project (3GPP) radio communication technology,for example Universal Mobile Telecommunications System (UMTS), Freedomof Multimedia Access (FOMA), 3GPP Long Term Evolution (LTE), 3GPP LongTerm Evolution Advanced (LTE Advanced), Code division multiple access2000 (CDMA2000), Cellular Digital Packet Data (CDPD), Mobitex, ThirdGeneration (3G), Circuit Switched Data (CSD), High-SpeedCircuit-Switched Data (HSCSD), Universal Mobile TelecommunicationsSystem (Third Generation) (UMTS (3G)), Wideband Code Division MultipleAccess (Universal Mobile Telecommunications System) (W-CDMA (UMTS)),High Speed Packet Access (HSPA), High-Speed Downlink Packet Access(HSDPA), High-Speed Uplink Packet Access (HSUPA), High Speed PacketAccess Plus (HSPA+), Universal Mobile TelecommunicationsSystem-Time-Division Duplex (UMTS-TDD), Time Division-Code DivisionMultiple Access (TD-CDMA), Time Division-Synchronous Code DivisionMultiple Access (TD-CDMA), 3rd Generation Partnership Project Release 8(Pre-4th Generation) (3GPP Rel. 8 (Pre-4G)), 3GPP Rel. 9 (3rd GenerationPartnership Project Release 9), 3GPP Rel. 10 (3rd Generation PartnershipProject Release 10), 3GPP Rel. 11 (3rd Generation Partnership ProjectRelease 11), 3GPP Rel. 12 (3rd Generation Partnership Project Release12), 3GPP Rel. 13 (3rd Generation Partnership Project Release 13), 3GPPRel. 14 (3rd Generation Partnership Project Release 14), 3GPP Rel. 15(3rd Generation Partnership Project Release 15), 3GPP Rel. 16 (3rdGeneration Partnership Project Release 16), 3GPP Rel. 17 (3rd GenerationPartnership Project Release 17) and subsequent Releases (such as Rel.18, Rel. 19, etc.), 3GPP 5G, 3GPP LTE Extra, LTE-Advanced Pro, LTELicensed-Assisted Access (LAA), MuLTEfire, UMTS Terrestrial Radio Access(UTRA), Evolved UMTS Terrestrial Radio Access (E-UTRA), Long TermEvolution Advanced (4th Generation) (LTE Advanced (4G)), cdmaOne (2G),Code division multiple access 2000 (Third generation) (CDMA2000 (3G)),Evolution-Data Optimized or Evolution-Data Only (EV-DO), Advanced MobilePhone System (1st Generation) (AMPS (1G)), Total Access CommunicationSystem/Extended Total Access Communication System (TACS/ETACS), DigitalAMPS (2nd Generation) (D-AMPS (2G)), Push-to-talk (PTT), MobileTelephone System (MTS), Improved Mobile Telephone System (IMTS),Advanced Mobile Telephone System (AMTS), OLT (Norwegian for OffentligLandmobil Telefoni, Public Land Mobile Telephony), MTD (Swedishabbreviation for Mobiltelefonisystem D, or Mobile telephony system D),Public Automated Land Mobile (Autotel/PALM), ARP (Finnish forAutoradiopuhelin, “car radio phone”), NMT (Nordic Mobile Telephony),High capacity version of NTT (Nippon Telegraph and Telephone) (Hicap),Cellular Digital Packet Data (CDPD), Mobitex, DataTAC, IntegratedDigital Enhanced Network (iDEN), Personal Digital Cellular (PDC),Circuit Switched Data (CSD), Personal Handy-phone System (PHS), WidebandIntegrated Digital Enhanced Network (WiDEN), iBurst, Unlicensed MobileAccess (UMA), also referred to as also referred to as 3GPP GenericAccess Network, or GAN standard), Zigbee, Bluetooth®, Wireless GigabitAlliance (WiGig) standard, mmWave standards in general (wireless systemsoperating at 10-300 GHz and above such as WiGig, IEEE 802.11ad, IEEE802.11ay, etc.), technologies operating above 300 GHz and THz bands,(3GPP/LTE based or IEEE 802.11p and other) Vehicle-to-Vehicle (V2V) andVehicle-to-X (V2X) and Vehicle-to-Infrastructure (V2I) andInfrastructure-to-Vehicle (I2V) communication technologies, 3GPPcellular V2X, DSRC (Dedicated Short Range Communications) communicationsystems such as Intelligent-Transport-Systems and others, the EuropeanITS-G5 system (i.e. the European flavor of IEEE 802.11p based DSRC,including ITS-G5A (i.e., Operation of ITS-G5 in European ITS frequencybands dedicated to ITS for safety re-lated applications in the frequencyrange 5,875 GHz to 5,905 GHz), ITS-G5B (i.e., Operation in European ITSfrequency bands dedicated to ITS non-safety applications in thefrequency range 5,855 GHz to 5,875 GHz), ITS-G5C (i.e., Operation of ITSapplications in the frequency range 5,470 GHz to 5,725 GHz)), etc.

Aspects described herein can be used in the context of any spectrummanagement scheme including dedicated licensed spectrum, unlicensedspectrum, (licensed) shared spectrum (such as LSA=Licensed Shared Accessin 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz and further frequencies andSAS=Spectrum Access System in 3.55-3.7 GHz and further frequencies).Applicable spectrum bands include IMT (International MobileTelecommunications) spectrum (including 450-470 MHz, 790-960 MHz,1710-2025 MHz, 2110-2200 MHz, 2300-2400 MHz, 2.4-2.4835 GHz (note: it isan ISM band with global availability and it is used by Wi-Fi technologyfamily (11b/g/n/ax) and also by Bluetooth), 2500-2690 MHz, 698-790 MHz,610-790 MHz, 3400-3600 MHz, 3400-3800 MHz, 3.55-3.7 GHz (note: allocatedfor example in the US for Citizen Broadband Radio Service), 5.15-5.25GHz and 5.25-5.35 GHz and 5.47-5.725 GHz and 5.725-5.85 GHz bands (note:allocated for example in the US (FCC part 15), consists four U-NII bandsin total 500 MHz spectrum), 5.725-5.875 GHz (note: allocated for examplein EU (ETSI EN 301 893)), 5.47-5.65 GHz (note: allocated for example inSouth Korea, 5925-7125 MHz and 5925-6425 MHz band (note: underconsideration in US and EU, respectively. Next generation Wi-Fi systemis expected to include the 6 GHz spectrum as operating band but it isnoted that, as of December 2017, Wi-Fi system is not yet allowed in thisband. Regulation is expected to be finished in 2019-2020 time frame),IMT-advanced spectrum, IMT-2020 spectrum (expected to include 3600-3800MHz, 3.5 GHz bands, 700 MHz bands, bands within the 24.25-86 GHz range,etc.), spectrum made available under FCC's “Spectrum Frontier” 5Ginitiative (including 27.5-28.35 GHz, 29.1-29.25 GHz, 31-31.3 GHz,37-38.6 GHz, 38.6-40 GHz, 42-42.5 GHz, 57-64 GHz, 71-76 GHz, 81-86 GHzand 92-94 GHz, etc), the ITS (Intelligent Transport Systems) band of 5.9GHz (typically 5.85-5.925 GHz), 5925-6425 MHz or part thereof and 63-64GHz, bands currently allocated to WiGig such as WiGig Band 1(57.24-59.40 GHz), WiGig Band 2 (59.40-61.56 GHz) and WiGig Band 3(61.56-63.72 GHz) and WiGig Band 4 (63.72-65.88 GHz), the 70.2 GHz-71GHz band, any band between 65.88 GHz, 57-64/66 GHz (note: this band hasnear-global designation for Multi-Gigabit Wireless Systems (MGWS)/WiGig.In US (FCC part 15) allocates total 14 GHz spectrum, while EU (ETSI EN302 567 and ETSI EN 301 217-2 for fixed P2P) allocates total 9 GHzspectrum), and 71 GHz, bands currently allocated to automotive radarapplications such as 76-81 GHz, and future bands including 94-300 GHzand above. Furthermore, the scheme can be used on a secondary basis onbands such as the TV White Space bands (typically below 790 MHz) wherein particular the 400 MHz and 700 MHz bands are promising candidates.Besides cellular applications, specific applications for verticalmarkets may be addressed such as PMSE (Program Making and SpecialEvents), medical, health, surgery, automotive, low-latency, drones, etc.applications.

Aspects described herein can also implement a hierarchical applicationof the scheme is possible, e.g. by introducing a hierarchicalprioritization of usage for different types of users (e.g.,low/medium/high priority, etc.), based on a prioritized access to thespectrum e.g. with highest priority to tier-1 users, followed by tier-2,then tier-3, etc. users, etc. Aspects described herein can also beapplied to different Single Carrier or OFDM flavors (CP-OFDM, SC-FDMA,SC-OFDM, filter bank-based multicarrier (FBMC), OFDMA, etc.) and inparticular 3GPP NR (New Radio) by allocating the OFDM carrier data bitvectors to the corresponding symbol resources.].

In the following, RLAN devices such as RLAN user equipments (UEs) andRLAN access points (APs) are described. Radio Local Area Networks(RLANs) are intended to cover smaller geographic areas like homes,offices and to a certain extent buildings being adjacent to each other.Radio LANs are also known as Wireless LANs (WLANs). A popular deploymentof Radio LANs is providing broadband connectivity at public locationslike airports, railway stations, conference centres, hotels and streetcafés. Even on trains and aboard aircraft Radio LANs are or will becomeavailable for providing network access. Radio LANs are also ratherpopular at home and at the office enabling the users to connect allequipment wirelessly. Currently, the frequency bands 2.4 GHz and 5 GHzare mainly used by Radio LANs and in many cases, the deployed technologyis based on the IEEE 802.11 standards family. However, othertechnologies such as LTE-LAA (Long Term Evolution License AssistedAccess) are deployed in those frequency bands as well.

Some of the features in this document are defined for the network side,such as Access Points, eNodeBs, etc. Still, a User Equipment (UE) maytake this role as well and act as an Access Points, eNodeBs, etc. I.e.,some or all features defined for network equipment may be implemented bya UE.

In the following detailed description, reference is made to theaccompanying drawings, which form a part thereof, and in which is shownby way of illustration specific aspects in which the disclosure may bepracticed. It is understood that other aspects may be utilized andstructural or logical changes may be made without departing from thescope of the present disclosure. The following detailed description,therefore, is not to be taken in a limiting sense. The following terms,abbreviations and notations will be used herein.

-   -   RLAN: Radio Local Area Network,    -   3GPP: 3rd Generation Partnership Project,    -   LTE: Long Term Evolution,    -   LTE-A: LTE Advanced, Release 10 and higher versions of 3GPP LTE,    -   BS: Base station, eNodeB,    -   FCC: Federal Communications Commission,    -   SAS: Spectrum Access System,    -   LSA: Licensed Shared Access    -   PA: Priority Access,    -   GAA: General Authorized Access,    -   PAL: Priority Access Licenses,    -   ASA: Authorized Shared Access,    -   CSS: Cloud Spectrum Services,    -   RF: Radio Frequency,    -   UE: User Equipment,    -   MIMO: Multiple Input Multiple Output,    -   TDD: Time Division Duplex,    -   FDD: Frequency Division Duplex,    -   CBSD: Citizen Broadband Radio Service Device

It is understood that comments made in connection with a describedmethod may also hold true for a corresponding device configured toperform the method and vice versa. For example, if a specific methodstep is described, a corresponding device may include a unit to performthe described method step, even if such a unit is not explicitlydescribed or illustrated in the figures. Further, it is understood thatthe features of the various exemplary aspects described herein may becombined with each other, unless specifically noted otherwise.

The described devices may include integrated circuits and/or passivesand may be manufactured according to various technologies. For example,the circuits may be designed as logic integrated circuits, analogintegrated circuits, mixed signal integrated circuits, optical circuits,memory circuits and/or integrated passives.

The methods and devices described herein may be configured to transmitand/or receive radio signals. Radio signals may be or may include radiofrequency signals radiated by a radio transmitting device (or radiotransmitter or sender) with a radio frequency lying in a range of about3 kHz to 300 GHz. The frequency range may correspond to frequencies ofalternating current electrical signals used to produce and detect radiowaves.

The methods and devices described hereinafter may be applied in SASsystems, e.g. SAS systems 100 as shown in FIG. 1 . The FCC (FederalCommunications Commission) released a Report and Order outlining therules for operating wireless devices in the 3.5 GHz band that spans from3550-3700 MHz. FCC released this spectrum for sharing with theincumbents, which means that the incumbents get priority in that bandand it can be used by broadband devices when (and where) incumbents arenot using the spectrum. The incumbents in this band include DoD radars.There are two additional tiers of spectrum users in addition to theincumbents namely the Priority Access (PA) and General Authorized Access(GAA). The Priority Access Licenses (PAL) users get protection from GAAusers which is similar to unlicensed spectrum.

The FCC also mandates a Spectrum Access System (SAS) that willcoordinate the spectrum use between the incumbents, PA and GAA. The SASis central to this band, and no tier 2 or tier 3 device can operateunless it is in constant communication with the SAS and receivesinformation of when and where to use the 3.5 GHz channels. The SAS hasto be approved by the FCC before it can be deployed. Since the SAS isthe central coordinator for this spectrum, it needs to have a lot ofinformation about the network and devices. In fact, FCC mandates most ofthis information to be contained in the SAS. FCC's Report and Orderoutlines a sample system with SAS(s) as shown in FIG. 1 . If there aremultiple SASs, they are supposed to be synchronized with each other.However, the FCC does not specify details of how the SAS have to beimplemented and what information has to be synchronized.

The methods and devices described hereinafter may be applied in LSA(Licensed Shared Access) systems, e.g. LSA systems 200 as shown in FIG.2 , ASA (Authorized Shared Access) systems and CSS (Cloud SpectrumServices) systems. The LSA (Licensed Shared Access) concept was recentlydeveloped by RSPG (Radio Spectrum Policy Group) on a European level. Theobjective is to propose a new way for answering to the operators' needsfor more spectrum. It is expected that no more dedicated spectrum willbe available for cellular operators for mobile communications in thefuture. LSA thus proposes mechanisms for introducing shared spectrumbased solutions, i.e. mobile cellular operators will have access toadditional licensed spectrum from other licensees (like public safety,government. etc.) which they normally would not get access to. LSA isbased on a similar solution as ASA (Authorized Shared Access). ASA,however, is limited to IMT spectrum while LSA is also addressing non-IMTbands. Both exist on a rather conceptual level for the time being.

A related technology is CSS (Cloud Spectrum Services) which addressesthe same framework as LSA and ASA, but introduces more detailedimplementation solutions. On a regulatory level, there is massiveinterest for LSA/ASA/CSS, in particular in Europe. CEPT WG FM has agreedto launch a corresponding project team. ETSI RRS has finalized theset-up of a so-called SRDoc (System Reference Document) which targets inparticular the 2.3-2.4 GHz Band which is expected to be one of the moststraightforward candidates for shared spectrum usage. This is alsoacknowledged by CEPT WG FM. CEPT has taken the inputs into account inits CEPT WG FM project teams PT52 and PT53. While current activitiesfocus on the 2.3-2.4 GHz band in Europe, it should be noted that theusage of the LSA concept is not limited to any specific frequency band.In fact, it is expected that the 2.3-2.4 GHz represents a first exerciseand in the future LSA usage will be extended to other bands.

The methods and devices described hereinafter may be applied in WiFi andBluetooth systems or any near field communication (NFC) technology. WiFiis a local area wireless computer networking technology that allowselectronic devices to connect to the network, mainly using the 2.4gigahertz (12 cm) UHF and 5 gigahertz (6 cm) SHF ISM radio bands. TheWi-Fi Alliance defines Wi-Fi as any “wireless local area network” (WLAN)product based on the IEEE 802.11 standards. However, the term “Wi-Fi” isused in general English as a synonym for WLAN since most modern WLANsare based on these standards. Many devices can use WiFi, e.g. personalcomputers, video-game consoles, smartphones, digital cameras, tabletcomputers and digital audio players. These can connect to a networkresource such as the Internet via a wireless network access point. Suchan access point (or hotspot) has a range of about 20 meters indoors anda greater range outdoors.

Bluetooth is a wireless technology standard for exchanging data overshort distances (using short-wavelength UHF radio waves in the ISM bandfrom 2.4 to 2.485 GHz) from fixed and mobile devices, and buildingpersonal area networks (PANs). It can connect several devices,overcoming problems of synchronization.

The methods and devices described hereinafter may be applied in LTE FDDmode as well as in LTE TDD mode systems, e.g. LTE mode systems having atype 1 LTE frame structure or LTE mode systems having a type 2 LTE framestructure. The type 1 LTE frame includes 10 sub-frames 204 each havingtwo slots 206. A basic type 1 LTE frame has an overall length of 10milliseconds. The type 2 LTE frame has an overall length of 10milliseconds. The 10 ms frame comprises two half frames, each 5 ms long.

The methods and devices described hereinafter may be applied in MIMOsystems. Multiple-input multiple-output (MIMO) wireless communicationsystems employ multiple antennas at the transmitter and at the receiverto increase system capacity and to achieve better quality of service. Inspatial multiplexing mode, MIMO systems may reach higher peak data rateswithout increasing the bandwidth of the system by transmitting multipledata streams in parallel in the same frequency band.

The FCC released a Report and Order on Apr. 17, 2015 “FCC REPORT ANDORDER AND SECOND FURTHER NOTICE OF PROPOSED RULEMAKING, FCC 15-47, Apr.21, 2015” outlining the rules for operating wireless devices in the 3.5GHz band that spans from 3550-3700 MHz. FCC released this spectrum forsharing with the incumbents, which means that the incumbents getpriority in that band and it can be used by broadband devices when (andwhere) incumbents are not using the spectrum. The incumbents in thisband include DoD radars. There are two additional tiers of spectrumusers in addition to the incumbents namely the Priority Access (PA) andGeneral Authorized Access (GAA). The Priority Access Licenses (PAL)users get protection from GAA users which is similar to unlicensedspectrum.

The FCC also mandates a Spectrum Access System (SAS) that willcoordinate the spectrum use between the incumbents, PA and GAA. The SASis central to this band, and no tier 2 or tier 3 device can operateunless it is in constant communication with the SAS and receivesinformation of when and where to use the 3.5 GHz channels. The SAS hasto be approved by the FCC before it can be deployed. Since the SAS isthe central coordinator for this spectrum, it needs to have a lot ofinformation about the network and devices. In fact, FCC mandates most ofthis information to be contained in the SAS. FCC's Report and Orderoutlines a sample system with SAS(s) as shown in FIG. 1 . If there aremultiple SASs, they are supposed to be synchronized with each other.However, the FCC does not specify details of how the SAS have to beimplemented and what information has to be synchronized.

Recently, several efforts have been made in order to present anindicative SAS architecture that accommodates the tiered access toshared spectrum. In Spectrum Access Systems (SAS), the GAA users areable to (1) have access to a database with information about incumbentusers' locations and frequency and (2) have access to the results of PALauctions and subsequent PAL frequency assignments. GAA users need tocheck if the SAS band is clear to use or not before startingtransmission. The incumbent usage will be informed or easy to detectbecause incumbent is transmitting at a high power.

FIG. 1 is a block diagram of a Spectrum Access System (SAS) 100 forspectrum management according to the FCC regulation. The SAS systemincludes an exemplary number of two central SAS coordinators 131, 132for coordinating spectrum use between incumbents, PA (priority access)users and GAA (general authorized access) users according to FCC(Federal Communications Commission) standardization.

The SAS communication system 100 includes an exemplary number of two SASentities (also referred to as SAS coordinator or SAS controller) 131,132, FCC databases 141 and an ESC (Environmental Sensing Capability)entity 142 which are coupled between each other. An exemplary number offour CBSD (Citizen Broadband Radio Service Devices) entities 111, 112,113, 114 are coupled with the SAS1 entity 131, where CBSD1, CBSD2 andCBSD3 are coupled via a proxy network manager 121. The CBSD devices maybe coupled to users 101, 102, 103, 104. In the example of FIG. 1 theCBSD1 device is connected to a first user 101 and a second user 102while CBSD4 device is connected to a third user 103.

The SAS entities 131, 132 have the following functionality: Enact andenforce all policies and procedures developed by the SAS Administrator;Determine and provide to CBSDs the permissible channels or frequenciesat their location; Determine and provide to CBSDs the maximumpermissible transmission power level at their location; Retaininformation on, and enforce, Exclusion Zones and Protection Zones;Communicate with the ESC to obtain information about federal IncumbentUser transmissions and instruct CBSDs to move to another frequency rangeor cease transmissions; Ensure that CBSDs operate in geographic areasand within the maximum power levels required to protect federalIncumbent Users from harmful interference; Register and authenticate theidentification information and location of the CBSDs; Ensure that CBSDsprotect non-federal incumbent users from harmful interference; ProtectPriority Accessed Licensees from interference caused by other PALs andfrom GAA users; Facilitate Coordination between GAA users operatingCategory B CBSDs; Resolve conflicting uses of the band while maintaininga stable radio frequency environment; Ensure secure and reliabletransmission of information between the SASs and the GBSDs.

FIG. 2 is a block diagram of a Licensed Shared Access (LSA) system 200as currently defined in Europe including an LSA controller 213 foradapting spectrum usage. The license shared access (LSA) communicationsystem 200 includes a LSA repository 211, an LSA controller 213, an OA&Mentity, an exemplary number of three incumbents 201, 202, 203 and apublic mobile communication system having an exemplary number of twobase stations BS1, BS2 and one exemplary user equipment UE connected tobase station BS1. The public mobile communication system provides alicensed spectrum 221 and an LSA spectrum 222.

The LSA repository 211 may store information on LSA spectrumavailability over time, space and frequency. The LSA controller 213 maybe used for controlling access to the LSA system. The OA&M entity 215may be used for maintaining operation of the LSA system.

While this disclosure mainly addresses the SAS case (US scenario) asshown in FIG. 1 , the basic principles are also applicable to theEuropean LSA context as shown in FIG. 2 .

FIG. 3 is a schematic diagram illustrating an exemplary WiFi stack 300.The WiFi stack 300 can be a typical WiFi product stack compliant to the802.11 protocol. The WiFi stack 300 includes (from bottom to top) aphysical (PHY) layer 306, a media access control (MAC) layer 305, a datastack 303, e.g. for TCP/UDP/IP communication, and an applications layer301. Optionally a MAC sublayer management entity (MLME) and a supplicant(security) layer 302 may be included. MLME stands for “MAC SublayerManagement Entity”. It provides various management procedures such asassociation, authentication etc.

As presented in this disclosure, existing 802.11 Access Points can beextended in a minimum invasive way such that WiFi equipment can be madecompliant to SAS and can be used as SAS GAA equipment.

In this disclosure a spectrum sharing context is considered, such as theFCC Citizen Broadband Radio System/Spectrum Access System (CBRS/SAS) in3.5 GHz as shown in FIG. 1 or the Licensed Shared Access (LSA) system in2.3-2.4 GHz in Europe as shown in FIG. 2 . In particular, in the CBRScontext, traditional RLAN systems (such as WiFi/MuLTEFire/etc.) can beused as so-called tier-3 devices. Changes over traditional RLAN systeminclude the requirement to vacate the band when the incumbent user iscoming in.

The disclosure presents a solution how to efficiently manage thevacating of a shared band by a RLAN system when the incumbent spectrumuser retakes the band. RLAN systems traditionally do not offer thepossibility to manage a higher-priority incumbent user. Existing RLANbands indeed do not foresee a hierarchical responsibility chain forspectrum access.

A basic idea according to this disclosure is to complement a classicalRLAN stack (as shown in FIG. 3 ) by an additional SAS SW stack which 1)Interacts with the RLAN stack on the Application Layer, i.e. on adriver-to-driver communication level (see left hand box in theillustration below which encapsulates the RLAN stack and the SAS SWstack); and 2) Interacts with an external SAS Controller. The SAScontroller will thus provide commands such as i) change band, ii) stopband usage, etc. and the SAS SW stack on the RLAN component willtranslate these SAS controller commands into specific instructions tothe classical RLAN stack. The driver-to-driver communication will beused in order to enforce the RLAN device into a mode which is suitablyprotecting the incumbent. Exemplary implementations of this basic ideaare described in the following.

FIG. 4 is a schematic diagram illustrating an exemplary SAS compliantWiFi equipment 400 according to the disclosure.

The idea is to add a second stack 420 into a WiFi equipment 300 whichonly interfaces through external standardized APIs 417 with the WiFistack 300 and is thus minimum invasive. The WiFi stack 300 correspondsto the WiFi stack 300 described above with respect to FIG. 3 . Theadditional SAS WiFi stack 420 includes an SAS applications layer whichinteracts through the external APIs 417 with the applications layer 301of the WiFi stack 300. The additional SAS WiFi stack 420 may include adata stack 422 with TCP/UDP/IP functionality that may interact (viaexternal APIs 424) with the data stack 442 with TCP/UDP/IP functionalityof the SAS central controller. Alternatively, the SAS applications layer421 of the additional SAS WiFi stack 420 may directly (without datastack) communicate with the SAS central controller applications layer441 of the SAS central controller. Alternatively, an SAS LBT (ListenBefore Talk) stack 430 may be included in the WiFi stack 300 which mayinteract via API interface 423 with the additional SAS WiFi stack 420.This LBT stack 430 can detect the Incumbents before transmitting data.If an Incumbent is available the WiFi network can be made silent.

The additional SAS WiFi stack 420 can provide all SAS related features.In some aspects of this disclosure, a concept is to include the“Additional SAS WiFi Stack” 420 into the original WiFi equipment 300.Since it only interacts through external interfaces 417 with theApplications layer 301, the approach is minimum intrusive.

The process is as follows: 1) If no incumbent is detected, the “SASApplications” layer 421 accesses WiFi through standard externalinterfaces and activates WiFi. 2) If an incumbent is detected (eitherthrough interfacing with the SAS Central Controller or (optionally)through LBT 430 in the WiFi Equipment 300, then the SAS Application 421puts the WiFi application on hold. Note that there is no need to fullyterminate the connection (which would be the standard way ofproceeding). Rather, the connection can be maintained but withoutaccessing the medium any more while the Incumbent is present. Once theincumbent is gone, using the existing connection can be simplycontinued. 3) The SAS Applications layer performs the following tasks:a) Access to SAS Central Controller in order to request information onpresence of Incumbent; b) Provide sensing data to SAS Central Controllerin case that the Incumbent is detected through the SAS LBT feature 430(in case it is available); c) Authorize usage of WiFi channel(s) to WiFistack 300 through external interfaces 417 (minimum intrusive); d) PutWiFi Communication on hold while incumbent is present or move WiFi toanother channel (following indications from SAS Central Controller).

To support the required features for incumbent protection, in anexemplary implementation the following new driver commands areintroduced for RLAN systems referring to the following actions: a) Groupcreation/management of Users/CBSDs (Grouping commands); b) Requestvacating of spectrum/Enable spectrum usage (Spectrum usage commands).

In the following, Examples of Grouping Commands are described. The firstset of commands enable SAS controller to group CBSDs (RLAN AccessPoints-APs) or the CBSD (AP) to group users (for example users in aspecific geographic location concerned by the arrival of an incumbent,users whose output power levels exceed a given threshold, etc.) and toassign a group ID to those CBSDs/users. The SAS SW stack (on the RLANdevice) enforces this grouping by the following new driver commands asshown below in Tables 1 and 2:

TABLE 1 Creation of group: the SAS or the CBSD (AP) sends this commandin order to create groups of CBSDs (APs)/users. Parameter Data Name TypeDescription groupLevel String The entity that enforces the grouping (itcan {‘SAS’, be either SAS to CBSD or CBSD to its ‘CBSD’} users) userIDString A unique identifier for a CBSD user cbsdID String A uniqueidentifier for each CBSD registered to SAS userMACaddr Number The MACaddress of the CBSD user cbsdMACaddr Number The MAC address of theregistered CBSDs groupID String A unique identifier for each group ofCBSDs or CBSD's users Example syntax: groupCreate(groupLevel,userID/cbsdID, userMACaddress/cbsdMACaddress, groupID).

TABLE 2 Manage groups: the SAS/CBSD sends this command in order toadd/remove entities to/from a group with a specific id. Parameter DataName Type Description groupLevel ‘SAS’ or The entity that enforces thegrouping (it can ‘CBSD’ be either SAS to CBSD or CBSD to its users)groupAction String The action that is applied by the SAS/CBSD {“add”, tothe group “rmv”, add→a CBSD/user is added to the group “end”} rmv→aCBSD/user is removed from the group end→the group is terminated groupIDString A unique identifier for each group of CBSDs userID String Aunique identifier for a CBSD user - required only in case of “add/rmv”actions cbsdID String A unique identifier for each CBSD registered toSAS - required only in case of “add/rmv” actions userMACaddr Number TheMAC address of the CBSD user - required only in case of “add/rmv”actions cbsdMACaddr Number The MAC address of the registered CBSDs -required only in case of “add/rmv” actions Example syntax:groupManage(groupLevel,action,groupID, userID/cbsdID,userMACaddress/cbsdMACaddress).

In the following, Examples of Spectrum Usage Commands are described. Thesecond set of commands refers to enforcement of spectrum usage actions(i.e. stop band etc.) and it includes two different cases. In the firstcase, the SAS fully terminates the access of a CBSD to a specific band(e.g. in case the incumbent has to use the channel and there is notanother available channel for the CBSD). In the second one, the SASmodifies the current CBSDs' transmissions so as to prevent anyinterference with the incumbent user (e.g. SAS changes the channel ofthe low-priority users, eliminate the power etc.).

In order to terminate the access/transmission of a CBSD to a specificband, the SAS can select among a set of different strategies and thecorresponding commands according to Tables 3 and 4 shown below:

TABLE 3 Enforcement of sleep mode to the CBSDs (APs): the SAS sends thiscommand to enforce either a specific CBSD (cbsdID) or a group of CBSDs(groupID) to enter in sleep mode and stop the transmission. ParameterData Name Type Description cbsdID String A unique identifier for eachCBSD registered to SAS groupID String A unique identifier for each groupof CBSDs termEvent String The event that terminates the sleep mode ofthe {“trigger”, CBSDs. “time”} If termEvent = trigger → another command(sleepStop) is needed to terminate the sleep mode If termEvent = time→sleep mode is terminated at the X (where x is given by endtimeparameter) endtime Number Timestamp that refers to the termination ofthe sleep mode - Required only if termEvent = time Example syntax:sleepEnforce(cbsdID/groupID, termEvent, endtime).

TABLE 4 Termination of sleep mode for the CBSDs (APs): the SAS sendsthis command to terminate the sleep mode either for a specific CBSD(cbsdID) or a group of CBSDs (groupID). Parameter Data Name TypeDescription cbsdID String A unique identifier for each CBSD registeredto SAS groupID String A unique identifier for each group of CBSDsExample syntax: sleepStop(cbsdID/groupID).

Instead of sleep-mode enforcement, the SAS can also use a set ofalternative techniques to block/unblock CBSDs (APs) based on specificparameters (e.g. MAC/IP address, application, content etc.) as shown inTable 5 below.

TABLE 5 The SAS can also use a set of alternative techniques toblock/unblock CBSDs (APs) based on specific parameters (e.g. MAC/IPaddress, application, content etc.) Parameter Data Name Type Descriptionaction String The action that is enforced to CBSDs {“block”, “unblock”}blockParam String The parameter that is checked by the SAS in {“IPaddr”,order to block specific CBSDs “MACaddr”, If blockParam = IPaddr/MACaddr→ “protocol”, CBSDs with specific IP/MAC addresses “app”} (defined inblockValue) are blocked If blockParam = protocol/app→ CBSDs that runspecific protocols/apps (defined in blockValue) are blocked blockValueString The values of the blockParameter that are blocked Example syntax:blockCBSD(action,blockParam,blockValue).

Instead of fully terminating the access of a CBSD to a given band, thefollowing alternative strategies may be employed in order to eliminatethe caused interference to incumbent user. The first alternative asshown in Table 6 is channel change and the second alternative strategyas shown in Table 7 is output power modification.

TABLE 6 Channel change: the SAS sends this command in order to enforcespecific CBSDs to “hop” to another available channel. Parameter DataName Type Description cbsdID String A unique identifier for each CBSDregistered to SAS channelTgt Number The target channel to which the CBSDis forced to hop Example syntax: channelChange(cbsdID, channelTgt).

TABLE 7 Output power modification: the SAS sends this command in orderto modify the transmission power of specific CBSDs. Parameter Name DataType Description cbsdID String A unique identifier for each CBSDregistered to SAS. Maxpower Number The maximum transmission power level(dBm/MHz) of the CBSD Example syntax: powerModify(cbsdID), maxpower).

FIG. 5 is an exemplary message sequence chart illustrating an exemplarymessaging 500 between SAS entities according to the disclosure when anIncumbent arrives. In FIG. 5 , the following network entities aredepicted: RLAN UE 511, (classical) RLAN component 512, SAS Software (SW)Stack 513, SAS Controller 514 and Incumbent 515.

The SAS SW stack 503 that may be implemented in the RLAN component 502for example can execute the following sequence of commands as soon as anincumbent 515 arrives—as can be seen from FIG. 5 : 1) Receive shut-downrequest from SAS Controller (based on the metrics→from project slides);2) SAS-Stack Creates suitable User Groups; 3) Enforce sleep mode forspecific User Groups; 4) Receive trigger from SAS Controller toterminate sleep mode; and 5) Execute termination of sleep mode throughAP commands.

In the Example illustrated in FIG. 5 , the message sequence may be asfollows: The incumbent 505 transmits “Request Spectrum” message 511 tothe SAS controller 504 to indicate that spectrum is required byincumbent 505. The SAS controller 504 transmits “Request Vacating ofSpectrum” message 512 to SAS SW stack 503 to indicate that spectrum isrequired by incumbent 505. In the SAS SW stack 503 groups of usersaffected by vacating of spectrum are created 513. Then, SAS SW stack 503transmits “request creation of user groups” message 514 to RLAN 502 torequest for creation of user groups. RLAN 502 answers withAcknowledgement 515. The SAS SW stack 503 then prepares for vacatingaction (e.g. sleep mode, blocking of MAC addresses, etc.) 516 andtransmits message “issue vacating request to user groups” to RLAN 502 toinform RLAN 502 about vacating request to user groups. RLAN 502transmits message “request users to vacate band” 518 to RLAN UE 501 toinform specific users about vacating request. RLAN UE 501 answers withAcknowledgement 519. Then, RLAN 502 transmits Acknowledgement 520 to SASSW stack 503 which transmits Acknowledgement 521 to SAS controller 504which transmits Acknowledgement 522 to Incumbent 505.

FIG. 6 is an exemplary message sequence chart illustrating an exemplarymessaging 600 between SAS entities according to the disclosure when theIncumbent does not require the spectrum resource any more. In FIG. 6 ,the same network entities as shown in FIG. 5 are depicted: RLAN UE 511,(classical) RLAN component 512, SAS Software (SW) Stack 513, SASController 514 and Incumbent 515. As soon as the incumbent does not needthe spectrum resource any more, the RLANs are triggered again and canuse spectrum again as illustrated in FIG. 6 .

In the Example illustrated in FIG. 6 , the message sequence may be asfollows: The incumbent 505 transmits “Indicate Spectrum available forRLAN” message 611 to the SAS controller 504 to indicate that spectrum isavailable again.

The SAS controller 504 transmits “make spectrum available to RLAN”message 612 to SAS SW stack 503 to indicate that spectrum shall be madeavailable for RLAN 502. In the SAS SW stack 503 affected user groups areidentified and users transmission is enabled 613. Then, SAS SW stack 503transmits “indicate availability of spectrum to user groups” message 614to RLAN 502 to indicate RLAN 502 of availability of spectrum to usergroups. RLAN 502 transmits “indicate availability of spectrum to UE”message 615 to RLAN UE 501 to indicate the specific RLAN UE 501 aboutavailability of spectrum. RLAN UE 501 answers with Acknowledgement 616.Then, RLAN 502 transmits Acknowledgement 617 to SAS SW stack 503 whichtransmits Acknowledgement 618 to SAS controller 504 which transmitsAcknowledgement 619 to Incumbent 505.

The techniques disclosed above with respect to FIGS. 1 to 6 , inparticular the use of the above commands described with respect to FIGS.5 and 6 can also be applied to provide specific guarantees in case thatmultiple secondary systems need to share access to the band (for examplesystems such as WiFi and MuLTEFire existing in the same band) so as toensure their harmonious co-existence, e.g. as described in thefollowing.

Initially, the SAS Controller will require medium access budgetrequirements from the secondary systems in order to manage the spectralresources and allow access to the corresponding bands (e.g.MuLTEfire/WiFi APs will provide required resource requests). Therequirements can be expressed in terms of bandwidth share, throughput(e.g. minimum throughput), application types (e.g., social media,personal email, youtube, etc.) or other performance requests.

To ensure truthfulness of the secondary systems and guaranteeutilization and fairness of the spectrum distribution among thedifferent systems, different incentive and allocation mechanisms can beused. A simple approach is to introduce a penalty to the secondarysystems that do not completely use the allocated resources to preventthem from requesting for the entire bandwidth. Other approaches that canbe used include auction-based mechanisms [4] or market-based approaches.For example, the required information that the CBSDs have to send to theSAS can be proportional to their resource requests. Hence, littleadditional information is required in case of low resource requests(e.g., a 1% resource request is granted easily) whereas more informationis required for high resource requests (e.g., a 99% resource requestrequired detailed information on application types, etc.).

Based on the requests, the SAS can assign the CBSDs to specific groupsusing the defined Grouping commands. In case of congestion orco-existence issues, the SAS Controller will determine an adequatetime-sharing scheme for each group in order to maximize spectrumutilization and minimize congestion issues. Based on this scheme, theSAS Controller informs the respective SAS stack so as to enforce thetime-sharing scheme by using the Spectrum Usage commands that aredefined above. This way, the SAS can block the transmission of specificgroups (either forcing sleep mode or using an alternative strategy) fora specific time duration so as different groups of CBSDs to beactive/inactive during non-overlapping time windows (see FIG. 7 ). Thegoal is to move the system operating point from a low efficiency stateto a high efficiency state, eliminating the traffic load.

The upper approach thus exploits the SAS Controller to manage resourcesharing between multiple distinct technologies (such as WiFi/MuLTEfire).

FIG. 7 is schematic diagram illustrating an exemplary workflow 700 forthe operation of CBRS tier-3 users according to the disclosure.

The workflow 700 in FIG. 7 illustrates the sequence of SAS and CBSDs'actions in case of incumbent detection as well as in case ofcongestion/co-existence issues due to multiple secondary technologies'co-existence. The diagram in FIG. 7 also indicates the use of thecorresponding commands for the SAS SW to RLAN interaction at each step.

The workflow 700 includes the following: In a first block 711 adetection is performed if congestion and/or co-existence issues exist.If yes, in a second block 712, SAS SW stack groups CBSDs. Groupingcommands are applied 713, e.g. groupCreate and/or groupManage asdescribed above. Then, in a third block 714 SAS SW schedules groups'transmissions. Spectrum usage commands are applied 715, e.g.sleepEnforce, blockCBSD. After third block 714 first block 711 isperformed again. If answer of first block 711 detection is no, fourthblock 716 is performed, where CBSDs operation is in a specific bandand/or channel. Then, in fifth block 717 detection of incumbent'stransmission by SAS is performed. If no, first block 711 is performedagain. If yes, sixth block 718 is performed in which spectrum requestfrom SAS Controller to SAS SW stack is transmitted, e.g. as describedabove with respect to FIGS. 5 and 6 . Then, in a seventh block 719, SASSW stack groups CBSDs, e.g. as described above. Grouping commands areapplied 720, e.g. groupCreate and/or groupManage as described above.

Then, in eighth block 721 existence of other available channels ischecked. If answer is yes, in ninth block 722 SAS SW enforces channelhopping of CBSD. Spectrum usage commands are applied 723, e.g.channelChange as described above. If answer of eighth block 721 is no,in tenth block 727, SAS SW enforces sleep mode or blocking of CBSDs.Spectrum usage commands are applied 728, e.g. sleepEnforce, blockCBSD asdescribed above. SAS SW enforces sleep mode or blocking of CBSDs as longas incumbent does not stop transmission 726. If Incumbent stopstransmission 726, in an eleventh block 724 SAS SW terminates sleep modeor blocking of CBSDs. Spectrum usage commands are applied 725, e.g.sleepStop and blockCBSD as described above.

FIG. 8 is an exemplary access point (AP) device 800 according to thedisclosure. The AP device may control spectrum usage of a hierarchicalcommunication system, in which a spectrum reserved for an Incumbent isusable by at least one user equipment (UE) for transmission when thespectrum is not required by the Incumbent, e.g. as described above withrespect to FIGS. 4 to 7 . The AP device 800 includes a processor 801.The processor 801 is configured to enforce the at least one UE into amode protecting use of the spectrum by the Incumbent (e.g. bytransmitting message “request user to vacate band” 812) based on aspectrum request indication (e.g. message “request vacating of spectrum”811) from the Incumbent, e.g. as described above with respect to FIGS. 4to 7 . The processor 801 is further configured to enable transmission ofthe at least one UE using the spectrum reserved for the Incumbent (e.g.by transmitting message “indicate availability of spectrum” 814) basedon a spectrum availability indication from the Incumbent (e.g. message“make spectrum available” 813).

The AP device 800 may correspond to the RLAN component 502 with SAS SWstack 503 depicted in FIGS. 5 and 6 or to the AP device 400 depicted inFIG. 4 or to any of the base stations BS1, BS2 depicted in FIG. 2 or toany of the CBSD devices 111, 112, 113, 114 depicted in FIG. 1 . Thecentral controller may correspond to the SAS controller 504 depicted inFIGS. 5 and 6 or to the SAS Central Controller 440 depicted in FIG. 4 orto the SAS1 controller 131 or SAS2 controller 132 depicted in FIG. 1 orto the LSA Controller 213 depicted in FIG. 2 or to the centralcontroller 900 depicted in FIG. 9 . The UE may correspond to one of theuser equipments 101, 102, 103 depicted in FIG. 1 or to the UE depictedin FIG. 2 or to the RLAN UE 501 depicted in FIGS. 5 and 6 . TheIncumbent may correspond to the Incumbent 505 depicted in FIGS. 5 and 6or to one of the Incumbents 201, 202, 203 shown in FIG. 2 .

Note that the Incumbent according to this disclosure may also representany device that has a higher priority for using the radio resources ofthe communication system than the UEs. For example the Incumbent mayalso represent a UE having a higher priority, for example by contractwith a system operator.

The AP device 800 may include a network interface (right side of FIG. 8) with a controller of the hierarchical communication system, inparticular a Spectrum Access System (SAS) controller or a LicensedShared Access (LSA) system controller. The processor 801 may beconfigured to receive the spectrum request indication 811 and/or thespectrum availability indication 813 via the network interface.

The processor 801 may receive a message 811 requesting vacating of thereserved spectrum from the controller of the hierarchical communicationsystem, e.g. from the central controller 900 depicted in FIG. 9 upon aspectrum request indication from the Incumbent. The processor 801 mayreceive a message 813 making the reserved spectrum available fortransmission of the at least one UE from the controller of thehierarchical communication system upon a spectrum availabilityindication from the Incumbent, e.g. as described above with respect toFIGS. 5 and 6 .

The AP device 800 may further include a user interface (left side ofFIG. 8 ) with the at least one UE, in particular at least one RLAN UE.The processor 801 may be configured to transmit a message 812 enforcingthe at least one UE into the mode protecting use of the spectrum by theIncumbent via the user interface to the at least one UE. The processor801 may be configured to transmit a message 814 enabling transmission ofthe at least one UE using the reserved spectrum via the user interfaceto the at least one UE.

The processor 801 may create groups of users affected by the spectrumrequest indication from the Incumbent. The processor 801 may preparevacating action to the affected groups of users, in particular vacatingaction comprising sleep mode and/or blocking of MAC addresses. Theprocessor 801 may transmit a message requesting users to vacate thereserved spectrum to UEs belonging to the affected groups of users. Theprocessor 801 may identify groups of users affected by the enforcementinto the mode protecting use of the spectrum by the Incumbent based onthe spectrum availability indication from the Incumbent, e.g. asdescribed above with respect to FIGS. 5 and 6 . The processor 801 maytransmit a message indicating availability of the reserved spectrum toUEs belonging to the affected groups of users, e.g. as described abovewith respect to FIGS. 5 and 6 .

The AP device 800 may include a first application programming circuitry802 configured to control the at least one UE. The AP device 800 mayinclude a second application programming circuitry 803 comprising aninterface with the first application programming circuitry 802. Thesecond application programming circuitry 803 may interact with a centralcontroller of the hierarchical communication system in order to allowthe central controller take over control of the at least one UE via theinterface with the first application programming circuitry 802, e.g. asdescribed above with respect to FIG. 4 .

The first application programming circuitry 802 may correspond to theWiFi Stack 300 described above with respect to FIG. 4 . The secondapplication programming circuitry 803 may correspond to the additionalSAS WiFi Stack 420 described above with respect to FIG. 4 .

The first application programming circuitry 802 may be coupled to the atleast one UE via a decentralized wireless communication network, inparticular via a WiFi network. The second application programmingcircuitry 803 may interact with the first application programmingcircuitry 802 via a first external application programming interface(API) 417 as shown in FIG. 4 . The second application programmingcircuitry 803 may interact with the central controller 440 via a secondexternal application programming interface (API) 424 as shown in FIG. 4.

The second application programming circuitry 803 may comprise a datastack 422 configured to interact with a corresponding data stack 442 ofthe central controller 440 via the second external API. The firstapplication programming circuitry 802 may comprise a WiFi stack. Thesecond application programming circuitry 803 may be coupled via anInternet Protocol (IP) interface 424 with the central controller 440 ofthe hierarchical communication system as shown in FIG. 4 .

FIG. 9 is a block diagram illustrating an exemplary central controller900, e.g. an SAS controller according to the disclosure.

The central controller 900 is a controller of a hierarchicalcommunication system, in which a spectrum reserved for an Incumbent isusable by at least one user equipment (UE) for transmission when thespectrum is not required by the Incumbent, e.g. as described above withrespect to FIGS. 4 to 9 . The central controller 900 comprises aprocessor 901.

The processor 901 is configured to indicate an access point (AP) device(connected at the left side of FIG. 9 with the AP device 900) to enforcethe at least one UE into a mode protecting use of the spectrum by theIncumbent (e.g. via message “request vacating of spectrum” 811 depictedin FIG. 9 ) based on a spectrum request indication 911 from theIncumbent (arriving from an Incumbent at the right side of FIG. 9 ).

The processor 901 is further configured to indicate the AP device toenable transmission of the at least one UE using the spectrum reservedfor the Incumbent Incumbent (e.g. via message “make spectrum available”813 depicted in FIG. 9 ) based on a spectrum availability indication 913from the Incumbent.

The central controller 900 may correspond to the SAS controller 504depicted in FIGS. 5 and 6 or to the SAS Central Controller 440 depictedin FIG. 4 or to the SAS1 controller 131 or SAS2 controller 132 depictedin FIG. 1 or to the LSA Controller 213 depicted in FIG. 2 . TheIncumbent may correspond to the Incumbent 505 depicted in FIGS. 5 and 6or to one of the Incumbents 201, 202, 203 shown in FIG. 2 . The APdevice may correspond to the RLAN component 502 with SAS SW stack 503depicted in FIGS. 5 and 6 or to the AP device 400 depicted in FIG. 4 orto any of the base stations BS1, BS2 depicted in FIG. 2 or to any of theCBSD devices 111, 112, 113, 114 depicted in FIG. 1 or to the AP device800 depicted in FIG. 8 . The UE may correspond to one of the userequipments 101, 102, 103 depicted in FIG. 1 or to the UE depicted inFIG. 2 or to the RLAN UE 501 depicted in FIGS. 5 and 6 .

The central controller 900 may include a Spectrum Access System (SAS)controller or a Licensed Shared Access (LSA) system controller asdescribed above with respect to FIGS. 1 and 2 .

The central controller 900 may include a network interface (right sideof FIG. 9 ) with the Incumbent. The processor 901 may receive thespectrum request indication 911 from the Incumbent via the networkinterface.

The processor 901 may transmit a message 811 requesting vacating of thereserved spectrum to the AP device upon the spectrum request indication911 from the Incumbent. The processor 901 may transmit a message 813making the reserved spectrum available for transmission of the at leastone UE upon the spectrum availability indication 913 from the Incumbent.

FIG. 10 is schematic diagram illustrating a method 1000 for controllingspectrum usage of a hierarchical communication system according to thedisclosure. In the hierarchical communication system a spectrum reservedfor an Incumbent is usable by at least one user equipment (UE) fortransmission when the spectrum is not required by the Incumbent, e.g. asdescribed above with respect to FIGS. 5 to 7 . The method 1000 includesenforcing 1001 the at least one UE into a mode protecting use of thespectrum by the Incumbent based on a spectrum request indication fromthe Incumbent, e.g. as described above with respect to FIGS. 4 to 9 .The method 1000 further includes enabling 1002 transmission of the atleast one UE using the spectrum reserved for the Incumbent based on aspectrum availability indication from the Incumbent, e.g. as describedabove with respect to FIGS. 4 to 9 .

The method 1000 may further comprise: receiving the enforcing and/or theenabling from a controller of the hierarchical communication system, inparticular a Spectrum Access System (SAS) controller or a LicensedShared Access (LSA) system controller, e.g. as described above withrespect to FIGS. 4 to 9 .

The method 1000 may further comprise: receiving a message requestingvacating of the reserved spectrum from the controller of thehierarchical communication system upon a spectrum request indicationfrom the Incumbent; and receiving a message making the reserved spectrumavailable for transmission of the at least one UE from the controller ofthe hierarchical communication system upon a spectrum availabilityindication from the Incumbent, e.g. as described above with respect toFIGS. 4 to 9 .

The method 1000 may further include: transmitting a message enforcingthe at least one UE into the mode protecting use of the spectrum by theIncumbent to the at least one UE; and transmitting a message enablingtransmission of the at least one UE using the reserved spectrum to theat least one UE, e.g. as described above with respect to FIGS. 4 to 9 .

The method 1000 may further include: creating groups of users affectedby the spectrum request indication from the Incumbent, e.g. as describedabove with respect to FIGS. 4 to 9 .

The method 1000 may further include: preparing vacating action to theaffected groups of users, in particular vacating action comprising sleepmode and/or blocking of MAC addresses.

The method 1000 may further include: transmitting a message requestingusers to vacate the reserved spectrum to UEs belonging to the affectedgroups of users, e.g. as described above with respect to FIGS. 4 to 9 .

The method 1000 may further include: identifying groups of usersaffected by the enforcement into the mode protecting use of the spectrumby the Incumbent based on the spectrum availability indication from theIncumbent, e.g. as described above with respect to FIGS. 4 to 9 .

The method 1000 may further include: transmitting a message indicatingavailability of the reserved spectrum to UEs belonging to the affectedgroups of users, e.g. as described above with respect to FIGS. 4 to 9 .

The method 1000 may further include: controlling the at least one UE bya first application programming circuitry; and interacting by a secondapplication programming circuitry with a central controller of thehierarchical communication system in order to allow the centralcontroller take over control of the at least one UE via the firstapplication programming circuitry, e.g. as described above with respectto FIGS. 4 to 9 .

The method 1000 may include the functionalities as described above withrespect to FIGS. 4 to 9 and may be performed by a processor, e.g. aprocessor on which the functionalities as described above with respectto FIGS. 4 to 9 are implemented as APIs.

FIG. 11 is an exemplary message sequence chart illustrating an exemplarymessaging 1100 of an interface between SAS SW stack 503 and AP/eNB 502according to the disclosure. The message sequence chart gives examplesfor messages on the interface 417 between additional SAS WiFi stack 420and WiFi stack 300 according to FIG. 4 that may be implemented asexternal API interface as shown in FIG. 4 .

An exemplary messaging on the interface 424 between SAS centralcontroller 440 and additional SAS WiFi stack 420 is also shown in FIG.11 . The SAS controller 504 transmits a message “request vacating ofspectrum” 512 to the SAS SW stack 503 which selects driver commandsbased on the received message 512, e.g. according to the descriptionwith respect to FIG. 4 . For example an enforcing of sleep mode commandis selected. The SAS SW stack 503 then transmits message “enforcetermination of TX” 1102 with the selected driver command, e.g. sleepmode to AP/eNB 502 which answers with ACK 1103. In section 1110 of themessage chart 1100 alternatives are depicted. If ACK is not received1111, the SAS SW stack 503 may transmit message “enforce shut Down” 1112to AP/eNB 502 in order to unconditionally shut down the respective UEsof AP/eNB 502. If ACK is received 1121, SAS SW stack 503 is not requiredto transmit further messages to AP/eNB 502.

In an exemplary implementation, the SAS controller 504 may assign timeslots to communication of UEs when using the spectrum reserved for theIncument. For example, each UE may have a time of 200 milliseconds fortransmission in the reserved frequency band.

The SAS controller 502 may schedule different systems of differentstructure, for example systems of different RAT (radio accesstechnology), etc. For example, different AP/eNBs 502 may be controlledby the SAS controller 504. One AP, for example, does not support allcommands transmitted by SAS controller 504. In this case, the AP 502 mayuse an alternative command that is next to the transmitted command. Forexample, if sleep mode is not supported, AP can perform a powershutdown. The AP may have proprietary commands that are similar to thecommands sent by SAS SW stack 503. In this case, AP can select aproprietary command that is similar or most similar to the commandtransmitted by SAS SW stack 503.

The disclosure also presents a user equipment (UE), e.g. a UE 101, 102,103 as shown in FIG. 1 or a UE as shown in FIG. 2 or an RLAN UE 501 asshown in FIGS. 5 and 6 , operating in a hierarchical communicationsystem, in which a spectrum reserved for an Incumbent is usable by theUE for transmission when the spectrum is not required by the Incumbent.The UE comprises a processor that is configured to switch the UE into amode protecting use of the spectrum by the Incumbent based on a handoverrequest to a first frequency band from a network device, e.g. a citizenbroadband radio system (CBRS). The handover request may result from aspectrum request indication from the Incumbent. The processor is furtherconfigured to enable transmission of the UE using the spectrum reservedfor the Incumbent based on a handover request to a second frequency bandfrom the network device, e.g. the CBRS. The second frequency band mayinclude at least part of the spectrum reserved for the Incumbent. Notethat in LSA, the incumbent may actively issue itself a spectrum requestindication. In SAS, however, the Incumbent is typically not interactingwith the SAS system, rather the SAS system has to detect that theIncumbent is in need to take back the spectrum. So, the trigger isfinally not coming from the Incumbent itself but from a detection(sensing) circuitry in the SAS system. Hence, the handover request tothe first frequency band is encompassing both. Also, the UE is typicallynot involved in the management/detection of such a trigger—this is onlyhandled within the CBSDs. The handover request may come from the CBSDs,but the trigger itself is invisible, i.e. transparent to the UE. For thehandover request to the second frequency, the same comments hold true,i.e. the trigger is transparent for the UE since it is managed at theCBSD level only. The UE only has received a handover (H/O) request toanother band (which can be seen as an indirect indication of such atrigger).

The UE may comprise a communication interface with an Access Point (AP)device, e.g. an AP device 800, 502, 400, BS1, BS2, 111, 112, 113, 114 asshown in FIGS. 8, 5, 6, 4, 1, 2 . The processor may receive the handoverrequest to the first frequency band, e.g. a spectrum request indicationand/or the handover request to the second frequency band, e.g. aspectrum availability indication via the communication interface fromthe AP device. The processor may switch the UE into a sleep mode uponreceiving the handover request to the first frequency band from the APdevice and may terminate the sleep mode upon receiving the handoverrequest to the second frequency band from the AP device.

In an exemplary implementation of the UE, the UE receives informationabout times at which the reserved frequency band is not available totransmission by the Incumbent. The UE may further receive informationabout which services are available in which frequency bands.

The UE may further receive information about frequencies, services,service classes, e.g. safety-related and/or non-safety-related,priorities, RATs, user groups, QoS, QoS dependent latency, block errorrates (BLER), packet error rates of the respective frequency bands.

In an exemplary implementation of the UE, the UE may transmitmeasurement data to the SAS controller 504 via AP device 502 and/or SASSW stack 503, for example sensing data, measurements about QoS levels ofthe reserved frequencies used by the UE. These measurement data may beused by the SAS controller 504 to decide which frequencies should byallocated to which UEs at what times. The SAS controller 504 may forexample switch off some APs for which errors have been detected based onthe measurement data from UEs.

In an exemplary implementation of the UE, the UE may transmitrequirements via AP 502 and/or SAS SW stack 503 to SAS controller 504,e.g. which QoS is required by UE, which error rates are tolerable by UE.The SAS controller 504 may configure the respective APs according to therequirements from UEs. For example, the SAS controller 504 mayprioritize the UEs and may divide UEs in hierarchical groups. Access tospecific APs may be allowed only for UEs belonging to specifichierarchical groups or having a specific priority. For example only UEsof the same hierarchy level or a lower or higher hierarchy level may beallowed to access specific APs.

In an exemplary implementation these requirements from the UEs may bedirectly transmitted to SAS controller 504, e.g. tunneled via SAS SWstack 503. For example, UE1 has specific QoS requirements to the networkand SAS controller 504 configures the network so to fulfill therequirements of UE1.

In an exemplary implementation, the RLAN system can include mobile edgecomputing nodes. In an exemplary implementation, UEs may form a fognetwork, e.g. a distributed fog network. These UEs may inform the SAScontroller about their requirements.

In an exemplary implementation, the UE may be able to performdevice-to-device (D2D) communication. In this scenario, the SAS SW stack503 may be implemented in the UE which is able to communicate directlywith the SAS controller 504 by traversing the AP 502. Then the UE mayperform AP functionality for other UEs.

The methods, systems and devices described herein may be implemented assoftware in a Digital Signal Processor (DSP), in a micro-controller orin any other side-processor or as hardware circuit on a chip or withinan application specific integrated circuit (ASIC).

Aspects described in this disclosure can be implemented in digitalelectronic circuitry, or in computer hardware, firmware, software, or incombinations thereof, e.g. in available hardware of mobile devices or innew hardware dedicated for processing the methods described herein.

The present disclosure also supports a computer program productincluding computer executable code or computer executable instructionsthat, when executed, causes at least one computer to execute theperforming and computing blocks described herein, in particular themethod 1000 as described above with respect to FIG. 10 and thetechniques described with respect to FIGS. 4 to 9 . Such a computerprogram product may include a readable storage medium storing programcode thereon for use by a processor, the program code comprisinginstructions for performing any of the methods as described above.

EXAMPLES

The following examples pertain to further aspects. Example 1 is anaccess point (AP) device for controlling spectrum usage of ahierarchical communication system, in which a spectrum reserved for anIncumbent is usable by at least one user equipment (UE) for transmissionwhen the spectrum is not required by the Incumbent, the AP devicecomprising a processor configured to: enforce the at least one UE into amode protecting use of the spectrum by the Incumbent based on a spectrumrequest indication from the Incumbent; and enable transmission of the atleast one UE using the spectrum reserved for the Incumbent based on aspectrum availability indication from the Incumbent.

In Example 2, the subject matter of Example 1 can optionally include: anetwork interface with a controller of the hierarchical communicationsystem, in particular a Spectrum Access System (SAS) controller or aLicensed Shared Access (LSA) system controller, wherein the processor isconfigured to receive the spectrum request indication and/or thespectrum availability indication via the network interface.

In Example 3, the subject matter of Example 2 can optionally includethat the processor is configured to: receive a message requestingvacating of the reserved spectrum from the controller of thehierarchical communication system upon a spectrum request indicationfrom the Incumbent; and receive a message making the reserved spectrumavailable for transmission of the at least one UE from the controller ofthe hierarchical communication system upon a spectrum availabilityindication from the Incumbent.

In Example 4, the subject matter of any one of Examples 1-3 canoptionally include a user interface with the at least one UE, inparticular at least one RLAN UE, wherein the processor is configured totransmit a message enforcing the at least one UE into the modeprotecting use of the spectrum by the Incumbent via the user interfaceto the at least one UE; and wherein the processor is configured totransmit a message enabling transmission of the at least one UE usingthe reserved spectrum via the user interface to the at least one UE.

In Example 5, the subject matter of any one of Examples 1-4 canoptionally include that the processor is configured to create groups ofusers affected by the spectrum request indication from the Incumbent.

In Example 6, the subject matter of Example 5 can optionally includethat the processor is configured to prepare vacating action to theaffected groups of users, in particular vacating action comprising sleepmode and/or blocking of MAC addresses.

In Example 7, the subject matter of any one of Examples 5-6 canoptionally include that the processor is configured to transmit amessage requesting users to vacate the reserved spectrum to UEsbelonging to the affected groups of users.

In Example 8, the subject matter of any one of Examples 1-7 canoptionally include that the processor is configured to identify groupsof users affected by the enforcement into the mode protecting use of thespectrum by the Incumbent based on the spectrum availability indicationfrom the Incumbent.

In Example 9, the subject matter of Example 8 can optionally includethat the processor is configured to transmit a message indicatingavailability of the reserved spectrum to UEs belonging to the affectedgroups of users.

In Example 10, the subject matter of any one of Examples 1-9 canoptionally include: a first application programming circuitry configuredto control the at least one UE; and a second application programmingcircuitry comprising an interface with the first application programmingcircuitry, wherein the second application programming circuitry isconfigured to interact with a central controller of the hierarchicalcommunication system in order to allow the central controller take overcontrol of the at least one UE via the interface with the firstapplication programming circuitry.

In Example 11, the subject matter of Example 10 can optionally includethat the first application programming circuitry is coupled to the atleast one UE via a decentralized wireless communication network, inparticular via a WiFi network.

In Example 12, the subject matter of any one of Examples 10-11 canoptionally include that the second application programming circuitry isconfigured to interact with the first application programming circuitryvia a first external application programming interface (API).

In Example 13, the subject matter of any one of Examples 10-12 canoptionally include that the second application programming circuitry isconfigured to interact with the central controller via a second externalapplication programming interface (API).

In Example 14, the subject matter of Example 13 can optionally includethat the second application programming circuitry comprises a data stackconfigured to interact with a corresponding data stack of the centralcontroller via the second external API.

In Example 15, the subject matter of any one of Examples 10-14 canoptionally include that the first application programming circuitrycomprises a WiFi stack.

In Example 16, the subject matter of any one of Examples 10-15 canoptionally include that the second application programming circuitry iscoupled via an Internet Protocol (IP) interface with the centralcontroller of the hierarchical communication system.

Example 17 is a central controller of a hierarchical communicationsystem, in which a spectrum reserved for an Incumbent is usable by atleast one user equipment (UE) for transmission when the spectrum is notrequired by the Incumbent, the central controller comprising a processorconfigured to: indicate an access point (AP) device to enforce the atleast one UE into a mode protecting use of the spectrum by the Incumbentbased on a spectrum request indication from the Incumbent; and indicatethe AP device to enable transmission of the at least one UE using thespectrum reserved for the Incumbent based on a spectrum availabilityindication from the Incumbent.

In Example 18, the subject matter of Example 17 can optionally include aSpectrum Access System (SAS) controller or a Licensed Shared Access(LSA) system controller.

In Example 19, the subject matter of any one of Examples 17-18 canoptionally include a network interface with the Incumbent, wherein theprocessor is configured to receive the spectrum request indication fromthe Incumbent via the network interface.

In Example 20, the subject matter of Example 19 can optionally includethat the processor is configured to: transmit a message requestingvacating of the reserved spectrum to the AP device upon the spectrumrequest indication from the Incumbent; and transmit a message making thereserved spectrum available for transmission of the at least one UE uponthe spectrum availability indication from the Incumbent.

Example 21 is a user equipment (UE) operating in a hierarchicalcommunication system, in which a spectrum reserved for an Incumbent isusable by the UE for transmission when the spectrum is not required bythe Incumbent, the UE comprising a processor configured to: switch theUE into a mode protecting use of the spectrum by the Incumbent based ona handover request to a first frequency band from a network device, inparticular a citizen broadband radio system, CBRS; and enabletransmission of the UE using the spectrum reserved for the Incumbentbased on a handover request to a second frequency band from the networkdevice.

In Example 22, the subject matter of Example 21 can optionally include acommunication interface with an Access Point (AP) device, wherein theprocessor is configured to receive the handover request to the firstfrequency band and/or the second frequency band via the communicationinterface from the AP device.

In Example 23, the subject matter of Example 22 can optionally includethat the processor is configured to switch the UE into a sleep mode uponreceiving the handover request to the first frequency band from the APdevice and to terminate the sleep mode upon receiving the handoverrequest to the second frequency band from the AP device.

In Example 24, the subject matter any one of Examples 21-22 canoptionally include that the handover request to the second frequencyband indicates time slots at which the reserved spectrum is availablefor transmission for the UE.

In Example 25, the subject matter any one of Examples 21-22 canoptionally include that the handover request to the second frequencyband indicates services which are usable for the UE.

In Example 26, the subject matter any one of Examples 21-22 canoptionally include that the processor is configured to determine aQuality-of-Service (QoS) of the reserved spectrum and to transmit theQoS to a central controller of the hierarchical communication system.

Example 27 is a method for controlling spectrum usage of a hierarchicalcommunication system, in which a spectrum reserved for an Incumbent isusable by at least one user equipment (UE) for transmission when thespectrum is not required by the Incumbent, the method comprising:enforcing the at least one UE into a mode protecting use of the spectrumby the Incumbent based on a handover request to a first frequency bandfrom a network device, in particular a CBRS; and enabling transmissionof the at least one UE using the spectrum reserved for the Incumbentbased on a handover request to a second frequency band from the networkdevice.

In Example 28, the subject matter of Example 27 can optionally include:receiving the enforcing and/or the enabling from a controller of thehierarchical communication system, in particular a Spectrum AccessSystem (SAS) controller or a Licensed Shared Access (LSA) systemcontroller.

In Example 29, the subject matter of Example 28 can optionally include:receiving a message requesting vacating of the reserved spectrum fromthe controller of the hierarchical communication system; and receiving amessage making the reserved spectrum available for transmission of theat least one UE from the controller of the hierarchical communicationsystem.

In Example 30, the subject matter of any one of Examples 27-29 canoptionally include: transmitting a message enforcing the at least one UEinto the mode protecting use of the spectrum by the Incumbent to the atleast one UE; and transmitting a message enabling transmission of the atleast one UE using the reserved spectrum to the at least one UE.

In Example 31, the subject matter of any one of Examples 27-30 canoptionally include: creating groups of users affected by the spectrumrequest indication from the Incumbent.

In Example 32, the subject matter of Example 31 can optionally include:preparing vacating action to the affected groups of users, in particularvacating action comprising sleep mode and/or blocking of MAC addresses.

In Example 33, the subject matter of any one of Examples 31-32 canoptionally include: transmitting a message requesting users to vacatethe reserved spectrum to UEs belonging to the affected groups of users.

In Example 34 the subject matter of any one of Examples 27-33 canoptionally include: identifying groups of users affected by theenforcement into the mode protecting use of the spectrum by theIncumbent based on the spectrum availability indication from theIncumbent.

In Example 35, the subject matter of Example 34 can optionally include:transmitting a message indicating availability of the reserved spectrumto UEs belonging to the affected groups of users.

In Example 36, the subject matter of any one of Examples 27-35 canoptionally include: controlling the at least one UE by a firstapplication programming circuitry; and interacting by a secondapplication programming circuitry with a central controller of thehierarchical communication system in order to allow the centralcontroller take over control of the at least one UE via the firstapplication programming circuitry.

Example 37 is a device for controlling spectrum usage of a hierarchicalcommunication system, in which a spectrum reserved for an Incumbent isusable by at least one user equipment (UE) for transmission when thespectrum is not required by the Incumbent, the device comprising: meansfor enforcing the at least one UE into a mode protecting use of thespectrum by the Incumbent based on a handover request to a firstfrequency band from a network device, in particular a CBRS; and meansfor enabling transmission of the at least one UE using the spectrumreserved for the Incumbent based on a handover request to a secondfrequency band from the network device.

In Example 38, the subject matter of Example 37 can optionally include:means for receiving the enforcing and/or the enabling from a controllerof the hierarchical communication system, in particular a SpectrumAccess System (SAS) controller or a Licensed Shared Access (LSA) systemcontroller.

Example 39 is an access point (AP) system for controlling spectrum usageof a hierarchical communication system, in which a spectrum reserved foran Incumbent is usable by at least one user equipment (UE) fortransmission when the spectrum is not required by the Incumbent, whereinthe AP system comprising a first processing component configured toenforce the at least one UE into a mode protecting use of the spectrumby the Incumbent based on a handover request to a first frequency bandfrom a network device, in particular a CBRS; and wherein the AP systemcomprises a second processing component configured to enabletransmission of the at least one UE using the spectrum reserved for theIncumbent based on a handover request to a second frequency band fromthe network device.

In Example 40, the subject matter of Example 39 can optionally include:a network interface with a controller of the hierarchical communicationsystem, in particular a Spectrum Access System (SAS) controller or aLicensed Shared Access (LSA) system controller, wherein the AP system isconfigured to receive the spectrum request indication and/or thespectrum availability indication via the network interface.

Example 41 is a computer readable non-transitory medium on whichcomputer instructions are stored which when executed by a computer causethe computer to perform the method of any one of Examples 27 to 36.

In addition, while a particular feature or aspect of the disclosure mayhave been disclosed with respect to only one of several implementations,such feature or aspect may be combined with one or more other featuresor aspects of the other implementations as may be desired andadvantageous for any given or particular application. Furthermore, tothe extent that the terms “include”, “have”, “with”, or other variantsthereof are used in either the detailed description or the claims, suchterms are intended to be inclusive in a manner similar to the term“comprise”. Furthermore, it is understood that aspects of the disclosuremay be implemented in discrete circuits, partially integrated circuitsor fully integrated circuits or programming means. Also, the terms“exemplary”, “for example” and “e.g.” are merely meant as an example,rather than the best or optimal.

Although specific aspects have been illustrated and described herein, itwill be appreciated by those of ordinary skill in the art that a varietyof alternate and/or equivalent implementations may be substituted forthe specific aspects shown and described without departing from thescope of the present disclosure. This application is intended to coverany adaptations or variations of the specific aspects discussed herein.

The invention claimed is:
 1. An access point (AP) device for controllingspectrum usage of a hierarchical communication system, in which aspectrum reserved for an Incumbent is usable by at least one userequipment (UE) for transmission when the spectrum is free of atransmission reservation by the Incumbent, the AP device comprising aprocessor configured to: receive a message from the Incumbent requestingvacating of a spectrum; generate a group of users affected by themessage from the Incumbent requesting vacating of the spectrum; andperform a spectrum management operation on the group of users; whereingenerating the group comprises assigning a group ID to a plurality ofusers affected by the message from the incumbent requesting vacating ofthe spectrum.
 2. The AP of claim 1, wherein performing the spectrummanagement operation comprises sending an instruction for the group ofusers to vacate the spectrum.
 3. The AP of claim 2, wherein theinstruction for the group of users to vacate the spectrum comprises aninstruction for the group of users to enter a sleep mode.
 4. The AP ofclaim 1, wherein performing the spectrum management operation comprisesblocking Media Access Control addresses of each user of the group ofusers.
 5. The AP of claim 1, wherein sending the instruction comprisessending the instruction to each user corresponding to the group ID. 6.The AP of claim 1, wherein generating the group of users affected by themessage from the incumbent requesting vacating of the spectrum comprisesgenerating a group of users utilizing the spectrum in the message fromthe incumbent.
 7. The AP of claim 1, wherein the AP is furtherconfigured to receive a spectrum availability indication from theIncumbent for use of the spectrum; wherein the spectrum managementoperation is a first spectrum management operation; and wherein the APis configured to perform a second spectrum management operation inresponse to the spectrum availability indication from the Incumbent. 8.The AP of claim 7, wherein the first spectrum management operationcomprises the AP sending an instruction to the group of users to vacatethe spectrum; and wherein the second spectrum operation comprises the APsending an instruction to the group of users that they may resume usingthe spectrum.
 9. The AP of claim 7, wherein the first spectrummanagement operation comprises the AP sending an instruction to thegroup of users enter a sleep mode; and wherein the second spectrumoperation comprises the AP sending an instruction to the group of usersto exit the sleep mode.
 10. The AP of claim 7, wherein the firstspectrum management operation comprises the AP blocking Media AccessControl addresses of each user of the group of users; and wherein thesecond spectrum operation comprises the AP stopping blocking MediaAccess Control addresses of each user of the group of users.
 11. The APdevice of claim 10, wherein the first application programming circuitryis coupled to the at least one UE via a decentralized wirelesscommunication network.
 12. The AP device of claim 10, wherein the secondapplication programming circuitry is configured to interact with thefirst application programming circuitry via a first external applicationprogramming interface (API).
 13. The AP device of claim 10, wherein thesecond application programming circuitry is configured to interact withthe central controller via a second external application programminginterface (API).
 14. The AP device of claim 10, wherein the secondapplication programming circuitry comprises a data stack configured tointeract with a corresponding data stack of the central controller viathe second external API.
 15. The AP of claim 1, further comprising anetwork interface with a controller of the hierarchical communicationsystem, wherein the controller comprises a Spectrum Access System (SAS)controller or a Licensed Shared Access (LSA) controller, wherein theprocessor is configured to receive the message from the incumbentrequesting vacating of the spectrum via the network interface.
 16. TheAP device of claim 1, comprising: a user interface with the at least oneUE, wherein the spectrum management operation comprises sending amessage to the group of users to force the group of users into a modeprotecting use of the spectrum by the Incumbent via the user interface;and wherein the processor is configured to send a message enablingtransmission of the group of users using spectrum via the user interfaceto the at least one UE.
 17. The AP device of claim 1, wherein theprocessor is configured to transmit a message to the group of usersindicating availability of reserved spectrum to UEs belonging to theaffected groups of users.
 18. The AP device of claim 1, comprising: afirst application programming circuitry configured to control a UEcorresponding to a user the in group of users; and a second applicationprogramming circuitry comprising an interface with the first applicationprogramming circuitry, wherein the second application programmingcircuitry is configured to interact with a central controller of thehierarchical communication system in order to allow the centralcontroller to take over control of the at least one UE via the interfacewith the first application programming circuitry.